System and method for streetlight monitoring diagnostics

ABSTRACT

One or more example diagnostics may be implemented as part of an intelligent luminaire manager or other radio frequency (RF) device that is in communication with an equipment or fixture such as a luminaire. Example diagnostics can determine a status such as a fixture malfunction, a cycling condition, a miswiring configuration, or another condition. The determined status can be wirelessly transmitted from the intelligent luminaire manager or other radio frequency device to a network server via a network. The network may be a network of intelligent luminaire managers and/or RF devices.

RELATED APPLICATION

The present application claims priority to U.S. Provisional ApplicationSer. No. 61/031,865, filed Feb. 27, 2008, and entitled “STREET LIGHTMONITORING SYSTEM,” which is hereby incorporated in its entirety byreference.

FIELD OF THE INVENTION

Aspects of the present invention relate generally to streetlightmonitoring, and more particularly to systems and methods for streetlightmonitoring diagnostics.

BACKGROUND OF THE INVENTION

It is estimated that there are more than 60 million outdoor lights inthe United States autonomously controlled by conventionalphoto-controls. These outdoor lights, when properly working, simplyreact to ambient light conditions, for example, to turn-on at dusk andturn-off at dawn. This method of operating outdoor lights results inmany lights being on when they are not needed, and it significantlyincreases outdoor lighting system operating costs.

The use of conventional photo-controls to control outdoor lights(luminaires) also leads to maintenance and repair issues. There aresignificant costs associated with hiring qualified maintenance personneland buying equipment such as, for example, special maintenance vehiclesrequired to access light fixtures for replacing lamps and servicingelectrical components. To discover faulty fixture operations, lightsystem owners and operators must resort to sending maintenance personnelto do “drive-by” visual examination of all units, which often number inthe thousands or wait for a customer to report a malfunction. Thisdrive-by must be done at night to detect non-functioning fixtures. Thesehigh costs limit how many lights can be repaired or serviced on anygiven day and force many light system operators to maintain theiroutdoor lights on an as needed basis (i.e., only when they are notifiedof an inoperable light). Understandably, this maintenance methodology ishighly inefficient because it ties up resources as crews and equipmentrandomly travel to failed, geographically dispersed outdoor lights.

SUMMARY OF THE INVENTION

According to an example embodiment of the invention, there is anintelligent luminaire manager. The intelligent luminaire managerincludes a voltage sensor for measuring a voltage provided to aluminaire; a current sensor for measuring a current provided to theluminaire; and a controller configured to receive voltage informationcorresponding to the voltage measured by the voltage sensor and currentinformation corresponding to the current measured by the current sensor.In addition, there is a luminaire diagnostic program stored in a memoryof the controller, where the luminaire diagnostic program is operativeto: compute a first average real power based upon the received voltageinformation and the received current information for a first timeperiod; compute a second average real power based upon the receivedvoltage information and the received current information for a secondtime period subsequent to the first time period; determine whether thesecond average real power has increased beyond the first average realpower by at least a preset amount; and generate a fixture statusindication associated with the luminaire based upon the determination.

According to another example embodiment of the invention, there isanother intelligent luminaire manager. The intelligent luminaire managerincludes a voltage sensor for measuring a voltage provided to aluminaire; a current sensor for measuring a current provided to theluminaire; and a controller configured to receive voltage informationcorresponding to the voltage measured by the voltage sensor and currentinformation corresponding to the current measured by the current sensor.In addition, there is a luminaire diagnostic program stored in a memoryof the controller, where the luminaire diagnostic program is operativeto: update a reference power value based upon an average real powercomputed using the received voltage information and the received currentinformation; compute a current real power based upon the receivedvoltage information and the received current information; increment acycling counter based upon determining, while the luminaire isassociated with an ON state, that the current real power is less than afirst threshold associated with the reference power value; and identifya cycling fault based upon the cycling counter exceeding a secondthreshold.

According to an example embodiment of the invention, there is yetanother intelligent luminaire manager. The intelligent luminaire managerincludes a first voltage sensor for measuring a line voltage received bythe intelligent luminaire manager; a second voltage sensor for measuringa load voltage associated with a luminaire; and a controller configuredto receive voltage information corresponding to voltages measured by thefirst and second voltage sensors. In addition, there is a luminairediagnostic program stored in a memory of the controller, where theluminaire diagnostic program is operative to: compare the line voltageto the load voltage; and determine a miswiring configuration associatedwith one or both of the intelligent luminaire manager and the luminairebased on the comparison of the line voltage to the load voltage.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 is a diagram illustrating a light management system according toan example embodiment of the invention.

FIG. 2 is a diagram illustrating street lights networked together usingintelligent luminaire managers according to an example embodiment of theinvention.

FIG. 3A is a diagram illustrating an intelligent luminaire manageraccording to an example embodiment of the invention.

FIG. 3B is a block diagram illustrating a luminaire and the intelligentluminaire manager of FIG. 3A according to an example embodiment of theinvention.

FIG. 3C is a circuit diagram illustrating a luminaire and theintelligent luminaire manager of FIG. 3A according to an exampleembodiment of the invention.

FIG. 3D is a circuit diagram further illustrating the intelligentluminaire manager of FIG. 3A according to an example embodiment of theinvention.

FIG. 4A is a diagram illustrating a network operation center accordingto an example embodiment of the invention.

FIG. 4B is a diagram illustrating geographically distributed networkoperational centers according to an example embodiment of the invention.

FIG. 5A is a diagram illustrating a light system owner/operatoraccording to an example embodiment of the invention.

FIG. 5B is a diagram illustrating an intelligent luminaire manager fieldunit according to an example embodiment of the invention.

FIG. 6 is a flow chart illustrating the blocks of a diagnostic methodfor determining a bad fixture, according to an example embodiment of theinvention.

FIG. 7 is a flow chart illustrating the blocks of a diagnostic methodfor determining cycling of a luminaire, according to an exampleembodiment of the invention.

FIG. 8A is a flow chart illustrating the blocks of a diagnostic methodfor a wire check algorithm, according to an example embodiment of theinvention.

FIG. 8B illustrates example wiring conditions, according to an exampleembodiment of the invention.

FIG. 9 is a flow chart illustrating the blocks of a diagnostic methodfor determining a fixture malfunction, according to an exampleembodiment of the invention.

FIG. 10 is a flow chart illustrating the blocks of a diagnostic method1000 for determining a dayburning malfunction, according to an exampleembodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention will now be described more fully hereinafter withreference to the accompanying figures, in which like numerals indicatelike elements throughout the several drawings. Some, but not allembodiments of the invention are described. Indeed, these inventions maybe embodied in many different forms and should not be construed aslimited to the embodiments set forth herein; rather, these embodimentsare provided so that this disclosure will satisfy applicable legalrequirements, be thorough and complete, and will fully convey the scopeof the invention to those skilled in the art.

FIG. 1 illustrates a light management system 100 having networkedintelligent luminaire managers 112 according to an example embodiment ofthe invention. As illustrated in FIG. 1, the light management system 100includes networks 102 a and 102 b, a network operation center 106, lightsystem owner/operators 108 a and 108 b, and third-party users 110. Thesesubsystems of system 100 are linked together using appropriatecommunication means such as, for example, radio frequencycommunications, optical communications and/or power line carrier to formcommunications backbone 104.

Each of the networks 102 a and 102 b includes several intelligentluminaire managers (ILMs) 112 and a master control 114. The intelligentluminaire managers 112 communicate with each other and with mastercontroller 114 using, for example, short-range radio frequency (RF)communication links. In an example embodiment, these RF communicationlinks operate in the 900 MHz unlicensed band and have a range of about1000 feet, but it will be appreciated that other frequencies and rangesmay be utilized as well. As described further below with reference toFIGS. 2 and 3, each of the intelligent luminaire managers 112 maycontrol operation and/or diagnostics of a light fixture, which may alsobe referred to as a luminaire.

Networks 102 a and 102 b in FIG. 1 each monitor and control operation ofa light system or subsystem. These light systems are represented asbeing operated and maintained by light system owner/operators 108 a and108 b respectively. Accordingly, data collected by intelligent luminairemanagers 112 a regarding the status of the light system represented bynetwork 102 a is forwarded to owner/operator 108 a. Data collected byintelligent luminaire managers 112 b regarding the status of the lightsystem represented by network 102 b is forwarded to owner/operator 108b. It will be appreciated that while networks 102 a and 102 b have beenillustrated as distinct networks, the networks 102 a and 102 b may beoperative with each other. For example, data collected by one ofintelligent network luminaire manages 112 a (in network 102 a) may beforwarded to another intelligent luminaire manager 112 b (in network 102b), and network 102 b may assist in the forwarding of the received datato the owner/operator 108 a. Owner/operators 108 a and 108 b also havethe capability to send commands to and/or reprogram operation of theintelligent luminaire managers coupled to their lights using the datanetwork shown in FIG. 1. This allows owner/operators 108 a and 108 b toadjust the operation of their respective light system.

In example embodiments of the invention, networks 102 may bepeer-to-peer networks, mesh networks, or a combination thereof. Thesenetworks may support, for example, three levels of devices: mastercontrollers 114; network routing devices, for example, intelligentluminaire manager 112; and other nodes such as RF device 202 (see FIG.2). However, it will be appreciated that the other nodes such as RFdevice 202 may also be configured as network routing devices as well,according to an example embodiment of the invention.

Each of the network links between intelligent luminaire managers 112includes a two-way communication channel. These two-way communicationchannels between intelligent luminaire managers 112 support, forexample, over the air or power-line carrier re-keying and re-programmingof these intelligent control devices. This allows for on-demand, turn-onand turn-off, for example, of selected street lights coupled tointelligent luminaire managers 112.

In an example embodiment, each intelligent luminaire manager 112maintains an internal clock which may be synchronized throughout theentire network or portions of the network. The clock may be local to thedevice and/or maintained at a selected location and transmitted to eachluminaire manager 112. This permits accurate date/time stamps to beadded to data sent to network operations center 106 and for time-basedcontrol of intelligent luminaire managers 112.

In example embodiments of the invention, the intelligent luminairemanagers 112 may support commands sent from master controller 114 toalternate or utilize different routing paths. Additionally, intelligentluminaire managers 112 may automatically attempt to reconnect to network102 if a signal is lost for more than a selected period of time (e.g.,after 15 minutes, after 30 minutes, after 60 minutes, etc.). Eachintelligent luminaire manager 112 is capable of rerouting data throughan alternative path, should one or more of the intelligent luminairemanagers 112 fail. When a failed or new intelligent network controller112 reenters network 102, other devices within the network pass on theactivation or installation of the new intelligent luminaire manager toother network routing devices.

Master controllers 114 a and 114 b may serve as gateways between theirassociated intelligent luminaire managers 112 and network operationcenter 106. It will also be appreciated that one or more intelligentluminaire managers 112 may also be configured to be a master controller114 as well. Each master controller 114 is coupled to network operationcenter (NOC) 106 through a communication backbone channel 104. Inembodiments, communication backbone channels 104 can be, for example,electrical and/or optical land line communication channels, satellitecommunication channels, paging network channels, power line carrierchannels, RF links, and/or cellular communication channels. Thesecommunication channels can include public and/or private communicationmeans (e.g., utility-owned lines and/or the Internet).

In an example embodiment, network operation center 106 couples to mastercontrollers 114 via an internet protocol infrastructure provided bythird-party carrier network services. Master controllers 114 mayoptionally provide data concentration and compression, and therebyreduce the overall service fees for third party leasing arrangements ofcommunication services. Master controllers 114 may also include a datastorage capability so that data to and from intelligent luminairemanagers 112 can be stored during network communication disruptions andtransmitted after communications are restored.

In an example embodiment, each master controller 114 may connect withnetwork operation center 106 at predetermined times and uploads thecurrent status of all intelligent luminaire managers 112 within its areaof responsibility and any devices that have entered network 102 sinceits last update to network operations center 106. For high-prioritycommunications, such as, for example, detection of a failed lamp, mastercontroller 114 may make unscheduled communications to network operationcenter 106. Many variations of communications between the mastercontroller 114 and the network operation center 106 are available inaccordance with example embodiments of the invention.

Each master controller 114 may be responsible for linking severalintelligent luminaire managers 112 to the network operation center 106.For example, in an example embodiment, more than 500 intelligentluminaire managers may be linked by a single master controller 114 tonetwork operation center 106, although fewer intelligent luminairemanagers may be linked as well. Each master controller 114 may beprogrammed from network operation center 106, according to an exampleembodiment of the invention.

In certain example embodiments, the master controller 114 may be capableof inheriting the features of network 102 routing devices, such asintelligent luminaire manager 112, for communications within network102. Master controller 114 also can implement, for example, a TCP/IPstack for communications over communication backbone channel 104 withnetwork operation center 106. Master controller 114 may also includememory such as non-volatile storage and cache data representing thestatus of all intelligent luminaire managers 112 for which it isresponsible.

As described in more detail below, in accordance with exampleembodiments, master controller 114 may provide authentication andauthorization to radio frequency devices (or other intelligent luminairemanagers) wanting to enter network 102. Master controller 114 maycommunicate with intelligent luminaire managers 112 and optimize routingwithin its network cluster. Master controller 114 may also includealternative power arrangements (e.g., solar power cells) or a backupenergy source (e.g., a battery) sufficient to power master controller114, for example, for up to 24 hours of operation.

Network operation center 106 may comprise one or more computerprocessors that are operable to execute one or more computer-executableinstructions for performing or directing one or more operations orservices as described herein. The network operation center 106 mayprovide a variety of services for light system owner/operators 108.These services include, for example, 24-hour-a-day, seven-day-a-weekdata storage and forwarding services for data flowing between lightsystem owner/operators 108 and their respective intelligent luminairemanagers 112. Network operation center 106 may be responsible forconfiguring, monitoring, and operating the router switches and othercommunication equipment that comprise the data network illustrated byFIG. 1. In an example embodiment, network operation center 106 maymanage and allocate internet protocol addresses and domain names for thedata network, manage and allocate nodes for the data network, andprovide database management services, network security management, andother network services. In addition, the network operation center 106may utilize the information, including status information, received fromone or more intelligent luminaire managers 112 in performingnetwork-level diagnostics, as described herein.

As illustrated in FIG. 1, network operation center 106 interfaces with aplurality of light system owner/operators 108 and/or other appropriateentities. Each light system owner/operator is shown comprising a lightsystem manager 109 and a maintenance unit 111.

Maintenance personnel 120 from the maintenance units may be responsiblefor repairing, replacing, and maintaining their own respective lightsystems. Maintenance personnel 120 may also be responsible for initialinstallation and activation of their intelligent luminaire managers 112with the aid of a wireless device such as a personal data assistant(PDA) hosted, intelligent luminaire manager field unit 122, or anothermicroprocessor based device. This field unit is described in more detailbelow with reference to FIGS. 5A and 5B.

In operation, the system 100 may perform as illustrated by the followingexample cycle of events. An owner/operator 108 of an outdoor lightsystem may wish to reduce operation and maintenance costs associatedwith his or her light system. The owner/operator 108 may therefore havemaintenance personnel 120 install and activate intelligent luminairemanagers 112, for example, as the conventional photo-controls arereplaced due to failures, according to an example embodiment of theinvention. A master controller 114 may also be installed in the vicinityof one of the intelligent luminaire managers 112 (e.g., on a nearby poleor building rooftop).

During the installation and activation of each intelligent luminairemanager 112, selected information such as the intelligent luminairemanager's identification number, GPS grid coordinates for the locationof the installation, the type (e.g., HID, non-HID, LED, etc.) of lightequipment being controlled, a digital photo of the installation, and/orinitial equipment parameters (e.g., electrical specifications such asvoltage and/or current specifications associated with the luminaire) iscollected by maintenance personnel 120 with the aid of the PDA-hostedfield unit 122. This information is then stored in the owner/operator'smaintenance system records and/or at the network operation center 106.In example embodiments, the PDA-hosted field unit 122 can communicatewith intelligent luminaire managers 112 as well as master controllers114 to receive information and/or upload information. Likewise, thePDA-hosted field unit 122 can likewise interface with the networkoperation center 106 to download selected information from thePDA-hosted field unit 122 to the network operation center 106.

Using the services of network operation center 106 and a computerconnected to network operation system 106 (e.g., via a secure Internetlink), the owner/operator 108 is able to monitor and control his or herlights. For example, if a light fails or is determined to be degraded,the intelligent luminaire manager 112 coupled to the light may send analarm to owner/operator 108, indicating that a failure has occurred oris likely to occur, via the network and network operation center 106.This alarm notifies light system owner/operator 108 of the changed lightsystem status and allows owner/operator 108 to take appropriate action.

In an example embodiment, the alarm may interact automatically with theowner/operator's maintenance program and may generate a work order thatinforms maintenance personnel 120 what actions are needed. The workorder might include, for example, the time of the alarm, the location ofthe degraded or failed equipment, and what equipment or parts are neededto correct the problem that caused the alarm. This work order may bedownloaded into the PDA-hosted field unit 122 and used to guidemaintenance personnel 120 to the site of the degraded or failedequipment. Once the repairs to the light are made, intelligent luminairemanager 112 may update the status for the light and the alarm may becleared. In an alternative embodiment, the alarm may be cleared whenowner/operator 108 updates his or her maintenance records, for example,using data collected by the intelligent luminaire manager field unit 122while the repair was being performed. In another embodiment, failure isonly reported to owner/operator 108 when the failure has occurred aspecified number of days in a row.

Once owner/operator 108 has installed intelligent luminaire managers onits lights, owner/operator 108 can control when the lights are turned-onand turned-off. This is achieved by sending commands over the datanetwork to individual or assignable groups of intelligent luminairemanagers 112 and/or reprogramming a control program stored in a memoryof each intelligent luminaire manager or group of assignable intelligentluminaire managers. More details regarding the functionality ofintelligent luminaire managers 112 is provided below.

Also shown in FIG. 1 are third-party users 110. Third-party users 110are managers/users of system 100 other than light system owner/operators108 and network operation center 106 personnel. For example, athird-party user 110 may be someone hired by an owner/operator 108 tooperate his or her light system or someone who is leasing, or otherwiseappropriately using, bandwidth in system 100 as explained in more detailbelow with reference to FIG. 2.

FIG. 2 illustrates a plurality of street lights 200 that form part of alight system operated and maintained by an owner/operator 108. Eachstreet light 200 is equipped with an intelligent luminaire manager 112mounted, for example, on top of a light fixture 204 of street lamp 200.In the embodiment shown, intelligent luminaire manager 112 may beconfigured and housed in an enclosure that conforms to appropriate NEMAand ANSI standards so that it can be exchanged one-for-one with aprior-existing photo-control used to control light fixture 204. Thiscompatibility allows an intelligent luminaire manager 112 to beinstalled on a light fixture 204 without requiring a new mount andwithout requiring any rewiring or physical modification of the fixture.Persons skilled in the relevant arts are familiar with industrystandards such as NEMA and ANSI C136 standards, and they willunderstand, based on the disclosure herein, how to adapt intelligentluminaire manager 112 for selected applications and customers.

As shown in FIG. 2, an intelligent luminaire manager 112 may communicateusing an RF communication link with its neighbors mounted on neighboringstreet lights 200. In an embodiment, an intelligent luminaire manager112 also is capable of communicating with other nearby devices thatinclude, for example, an RF device 202. This communication can beunidirectional or bidirectional. The unidirectional communication can befrom an RF device 202 to the intelligent luminaire manager 112 or fromthe intelligent luminaire manager 112 to RF device 202 depending onwhether RF device 202 is a transmitting device or a receiving device.Communication with an RF device 202 may be established when an RF device202 enters into the proximity or communication space of an intelligentluminaire manager 112 and is authorized to become a part of the networkformed by intelligent luminaire manager 112 and its neighbors.

In an example embodiment, the RF device 202 may become a part of anetwork by transmitting a signal that is received by a communicationsunit inside intelligent luminaire manager 112. Intelligent luminairemanager 112 then reports the presence of RF device 202 to networkoperation center 106, via the network and a master control 114. RFdevice 202 may be allowed to simply transmit data over the network, orit may be allowed to transmit and receive data. This communication canbe either open or encrypted. Intelligent luminaire manager 112 is ableto block communications from RF device 202 if RF device 202 is assessedto be functioning improperly or if the RF device's 202 access is deniedbased on a blacklist maintained by the network operations center 106 orif the RF device 202 is interfering with the routing of higher prioritytraffic.

In example embodiments of the invention, the RF device 202 may be ablind slave. A blind slave is a device controlled by intelligentluminaire manager 112. One example use of a blind slave is to controlthe operation of an outdoor light (e.g., a house porch light or adriveway light). The blind slave coupled to the light receives commandsfrom a nearby intelligent luminaire manager 112 to turn-on and turn-offthe light, for example, in conjunction with the luminaire controlled bythe intelligent luminaire manager 112. In one embodiment, blind slavesmay be controlled by a utility in order to limit power usage duringperiods of high power demand and thereby prevent brown-outs orblack-outs from occurring. The use of blind slaves is not limited tojust photo control.

In example embodiments of the invention, the communication links betweenintelligent luminaire managers 112 can include, for example, power linecarrier communication links or optical communication links. Thus,embodiments of the invention are not limited to using only RFcommunication links.

As described herein, the precise location of each intelligent luminairemanager device 112 is known or can otherwise be determined. Therefore,using appropriate algorithms, intelligent luminaire manager 112, mastercontroller 114 and/or network operation center 106 may be able toaccurately determine and report the location of any RF device 202. Forexample, in an example embodiment of the invention, master controller114 is able to calculate interpolated coordinates for an RF device 202based on information received from a variety of intelligent luminairemanagers 112 and the master controller's knowledge of the locations ofthese luminaire managers 112.

It will be appreciated that the potential for communicating with radiofrequency (RF) or radio frequency identification (RFID) type devicesusing the network formed by intelligent luminaire managers 112 is nearlyboundless, according to an example embodiment of the invention. Forexample, an RF device 202 might be included in a car and used to monitorand locate stolen cars as they pass by or park near streetlights 200. Anauto insurance company can pay a light system owner/operator to monitorfor and report the location of stolen cars using his or her network. Inthis example, an RF device 202 might be configured to start transmittinga stolen car signal, for example, whenever the car's engine was startedwithout using the car's ignition key. This stolen car signal would bedetected by an intelligent luminaire manager 112 and reported via thenetwork to an appropriate individual (e.g., a third-party user 110 suchas an insurance company representative and/or a local law enforcementofficial).

A similar use to that described above of the network capabilities ofintelligent luminaire managers 112 would be to identify and locate anindividual under house arrest, wearing an ankle bracelet, who has lefthis or her house. Other possible uses include, but are not limited to:providing security monitoring to determine if a nearby gate is open orclosed or whether a particular system is on or off; to provide aninterface to General Motor's ON-STAR system; to provide gun shotdetection; to provide auto traffic and pedestrian monitoring; to providepublic address audio communications and broadcast warning information(e.g., radiation alerts, bio alerts, chemical alerts, smog alerts,etc.); to provide high crime area surveillance; to locate lostindividuals, children and pets; to relay weather monitoring data, powermonitoring data, etc.; to repeat cellular communications, WiFicommunications, or Internet communications; and to read and/or relayelectric meter data, gas meter data, and/or water meter data for publicutilities. Still other uses will be available in accordance with otherexample embodiments of the invention.

FIG. 3A shows a detailed view of an enclosure 301 for intelligentluminaire manager 112 according to an embodiment of the invention. Asshown in FIG. 3A, housing 301 of intelligent luminaire manager 112includes a window 303 that exposes a photo-detector 305 to ambientlight. This allows intelligent luminaire manager 112 to be programmed toturn-on and/or to turn-off based on ambient light conditions in additionto an internal clock. A filter can be used to adjust thesensitivity/response of photo-detector 305 (e.g., a filter such as aninfrared filter can be used to prevent the unwanted turning-on andturning-off of a light due to passing clouds, sky condition or theinfluence of other nearby lights).

In an example embodiment, the intelligent luminaire manager 112 includesat least one LED (not shown) internal or external to enclosure 301 forcommunicating with maintenance crews. In one embodiment, the LEDtransmits infrared signals that are received by PDA-hosted field unit122. In another embodiment, the LED flashes a visual code that can beseen and interpreted by the maintenance crew. For example, when anintelligent luminaire manager 112 is initially installed, it sends amessage to a nearby intelligent luminaire manager 112 and receives backan acknowledgement signal. When this acknowledgment signal is receivedby the newly installed intelligent luminaire manager 112, its LED sendsor flashes a code to let the maintenance crew know that the signal hasbeen sent and an acknowledgement signal received. This lets themaintenance crew know that the intelligent luminaire manager 112 isworking properly. In an embodiment, an LED signal may be differentcolors to indicate different status. Likewise, another light emitterbesides an LED may be utilized in accordance with other exampleembodiments of the invention.

As noted herein, the enclosure 301 may conform to appropriate NEMA andANSI standards so that it can be installed on an intended light fixturewithout requiring a new mount and without requiring any rewiring orphysical modification of the fixture. In example embodiments, enclosure301 may be formed from a highly durable material, such as plastic, thatis appropriate for outdoor use and that will withstand the expectedweather and temperatures variations at the intended location ofinstallation. Enclosure 301 also can be coated with a weather-resistantmaterial.

In an example embodiment, each luminaire manager 112 or enclosure 301has one or more scannable barcodes securely attached for purposes ofidentification. An identification code can also be stored in a memory ofeach luminaire manager 112. In an example embodiment, PDA-hosted fieldunit 122 is used to read and/or write the identification code to thememory of each luminaire manager 112.

FIG. 3B is a block diagram that further illustrates the features andfunctionality of an intelligent luminaire manager 112 according to anexample embodiment of the invention. As shown in FIG. 3B, theintelligent luminaire manager 112 is coupled to and controls a light ormore precisely a luminaire 200. Luminaire 200 includes a ballast 302, astarter 306, and a lamp 308. Intelligent luminaire manager 112 includesa controller 310, a luminaire condition sensing and diagnostic subsystem312, a communications subsystem 314, and other optional subsystems 316.

In an example embodiment, luminaire 200 is a conventional luminaire suchas, for example, a street light. Controller 310 may include a processor318, memory 320, and an interface subsystem 322. Memory 320 stores avariety of programs and/or computer-executable instructions that areexecuted and/or implemented using processor 318. These programs and/orcomputer-executable instructions may include, for example, a luminairecontrol program 324, luminaire and intelligent luminaire managerconfiguration program 326, status reporting program 328, and otheroptional programs 330.

According to an example embodiment of the invention, an intelligentluminaire manager 112 may be utilized to turn-on and turn-off lamp 308on demand. Commands to turn-on and turn-off lamp 308 can be delivered tointelligent luminaire manager 112 via the data network illustrated inFIG. 1. In an example embodiment, data sent by an owner/operator 108over the network is used to program a luminaire control program 324stored in a memory 320 of intelligent luminaire manager 112. Thisprogram interacts with a network synchronized clock/timer function andsupports an on-time and an off-time for lamp 308 for each day of theweek with a one-minute time resolution. Example on-time and off-timecommands that can be programmed include: (1) turn on lamp 308 at time X,and turn off lamp 308 at time Y; (2) turn on lamp 308 at time X, andturn off lamp 308 Y minutes after it is turned on; (3) turn on lamp 308at dusk, and turn it off X minutes after it turns-on; and (4) turn onlamp 308 at dusk, and turn it off X minutes after dawn.

The above-described programmable commands to turn-on and turn-off lamp308 are illustrative only and not intended to limit embodiments of theinvention. Other programmable commands that can be also be used inaccordance with other example embodiments of the invention. For example,commands can be programmed to turn lamp 308 on only during certain daysof the week, to turn-on and turn-off lamp 308 at different times duringdifferent days in a given week, or all lamps in a group can be turned-onat a specified time and turned-off, for example, at dawn. In an exampleembodiment, selected lamps can be sent a command to turned-off duringperiods of high power demand. Likewise, turn-on and turn-off times canbe programmed to meet state or local light trespass codes, and these canbe re-programmed remotely if the light trespass codes change.

In an example embodiment, in the event an intelligent luminaire manager112 loses contact with network operations center 106 or mastercontroller 114, due for example to a network failure, intelligentluminaire manager 112 may maintain a current program or otherwise revertto a pre-stored program for controlling luminaire 200. For example, thiscould be to turn on lamp 308 at dusk and to turn it off at dawn.Intelligent luminaire manager 112 can tolerate and continue operatingthrough expected energy surges and sags without disruption of operation.

In an example embodiment, an intelligent luminaire manager 112 usesluminaire condition sensing and diagnostic subsystem 312 to monitor acondition or status associated with the luminaire 200. As describedherein, luminaire condition sensing and diagnostic subsystem 312 may beoperative to determine or detect a fixture malfunction, a cyclingcondition, or another fault or condition, which may be reported asstatus data or events/alarms to the owner/operator 108.

FIG. 3C is an example circuit diagram that further illustrates luminaire200 and intelligent luminaire manager 112 according to an exampleembodiment of the invention. The circuit diagram is illustrative and notintended to limit embodiments of the invention. As shown in FIG. 3C, inan example embodiment, intelligent luminaire manager 112 may be athree-prong device per ANSI C136.10 or similar standard that acts like aswitch to control the power supplied to luminaire 200. A first prong 301a of intelligent luminaire manager 112 connects to an energized line ofa power supply (not shown). A second prong 301 b of intelligentluminaire manager 112 connects to a neutral line or common of the powersupply. A third prong 301 c of intelligent luminaire manager 112connects to a load line of luminaire 200. The load line is attached toballast 302 and an optional power factor correction capacitor 304.Ballast 302 is connected to starter 306 (if used) and lamp 308. Optionalpower factor correction capacitor 304, starter 306, and lamp 308 areeach connected to the neutral line of the power supply.

FIG. 3D is a more detailed circuit diagram of an intelligent luminairemanager 112 according to an example embodiment of the invention. Asshown in FIG. 3D, power from the power supply is rectified by arectifier 350. Rectified power is filtered and regulated, and providedto controller 310. In an embodiment, controller 310 may be acommercially available microprocessor or microcontroller. Rectifiedpower is also provided to a pickup coil 354 of a relay 352. When acontrol signal provided by controller 310 closes a switch 356, pickupcoil 354 is energized and closes a contact of relay 352. As illustratedin FIG. 3D, the closing of the relay contact provides power to luminaire200.

As shown in FIG. 3D, two resistances 358 and 359 form a voltage dividernetwork. The voltage developed across resistance 359 is a referencevoltage (Vref) that is provided to controller 310 as an input parameter.A current sensor 357 is coupled between relay 352 and the load prong ofintelligent luminaire manager 112. Current sensor 357 generates areference current (Iref), which is also provided to controller 310 as aninput parameter. In an example embodiment, current senor 357 is acurrent transformer. In another example embodiment, current sensor 357is a current sensing resistor or Hall effect sensor. As describedherein, the input parameters Vref and Iref may be used in diagnosing andproviding an indication of the status or condition of luminaire 200. Itwill be appreciated that the voltage and current sensors described withrespect to FIG. 4D are provided for illustrative purposes only, and thatother voltage and current sensors are available in accordance with otherexample embodiments of the invention.

Based on the description contained herein, it will be appreciated thatsome or all of the functions and/or functionality described with regardsto intelligent luminaire manager 112 herein can be implemented, forexample, as an integral part of luminaire 200.

Similarly, functions and/or functionality described with respect toluminaire 200 (e.g., starter 306) can be implemented as a part ofintelligent luminaire manager 112. Thus, the illustration anddescription of specific functions and functionality residing inluminaire 200 and/or intelligent luminaire manager 112 is illustrativeand not intended to limit embodiments of the invention.

FIG. 4A is a more detailed depiction of a network operation center 106according to an example embodiment of the invention. As shown in FIG.4A, network operation center 106 includes a main server 400, a maindatabase 402, data backup 404, and data routing capabilities 406. Themain server 400 may comprise one or more computer processors that areoperable to execute one or more computer-executable instructions storedin one or more memories for performing or directing one or moreoperations or services as described herein. As described herein, networkoperation center 106 may provide one or more services, such as, forexample, main data network system operation and maintenance 408,subscriber/customer services 410, network security services 412, andsubscriber/customer data interface services 414. As used herein, theterm subscriber/customer refers to a light system owner/operator 108and/or a third-party user 110.

In an example embodiment, network operation services provided by networkoperation center 106 personnel include six major components: subscriberprovisioning, network provisioning, traffic engineering, billing,service assurance, and security management. Subscriber provisioningrefers to subscriber management, subscriber selection, and subscriberactivation. Network provisioning refers to capacity planning, networkdesign, and device provisioning. Traffic engineering refers to networktraffic analysis and policy management. Billing refers to, for example,both settlement of accounts between and amongst subscriber/customers,and usage data collection, rating, invoicing, and collection of bills.In an example embodiment, network operations center 106 records customerinformation for each intelligent luminaire manager 112 that can be usedby owner/operators 108 to support customer service queries and reportsand billing of their respective customers. Service assurance refers toasset management, performance management, service-level management,fault management, trouble management, and work-force management.Security management refers to access fraud, service fraud, managementaccess control, and denial of service. These network services may beprovide a framework that provides scalability for a unified wide-areanetwork platform that can be easily managed and controlled in real time,for example, over the internet using either standard web browsers orcustomer-specific applications developed within a software framework.Like the physical hardware of the network, the software may be scalable.

Scalability of the system can be ensured by distributing the necessarysoftware over multiple servers. In addition, this increases bothredundancy and reliability. A communications software program maintainedby network operation center 106 provides a virtual private network foreach gateway to the network operation center (e.g., master controllers114). Network operation center 106 is capable of supporting manythousands of concurrent subscribers. Notable features of networkoperation center 106 include its store and forward data managementtechnology; its management environment that supports and controls amassive subscriber base of mobile computers, integrated servers and webservice users; its security and data independence that facilitatessupporting large numbers of separate customers and their sensitivebusiness data; and its ability to provide fast, secure, andhighly-available synchronization between servers and thesubscriber/customer populations they support.

In an embodiment, network operation center 106 records GPS coordinatesfor each node location (e.g., the locations of intelligent luminairemanagers 112). This data is used to generate user display maps of nodelocations and to support workforce management reports that include nodelocations.

Network operation center 106, based on data collected, also is able toprovide detailed information to its subscribers/customer regarding thetype of fixture, lamp type, ballast type, and starter type operated byeach intelligent luminaire manager 112. Additionally, network operationcenter 106 software is able to generate summary failure analysisreports, broken down by lighting system attributes such as, for example,fixture type, lamp type, ballast type, starter type, and hours ofoperation. This analysis is provided to specific customers and/or allcustomers, based on how often a component fails or requires a servicecall. The analysis preferably includes failure conditions identified bythe network as well as information provided to call centers about thefailures.

In an example embodiment, a time stamp is provided with data packettransported via a network such that resolution about events on thenetwork can be identified, for example, within one minute. If aluminaire 200 controlled by an intelligent luminaire manager 112 fails,it preferably takes about one minute in this embodiment before an alarmis generated at an associated owner/operator's site. This alarmpreferably displays both the location of the failed luminaire and thetime of failure.

As shown in FIG. 4A, network operation center 106 maintains a database402 that includes the current status of all nodes in the data networksystem. In an example embodiment, the bandwidth of the network is suchthat it can support video. In an example embodiment, the networkoperation center 106, via the networks 102, forwards requests fromsubscribes/customers for information, such as, for example, voltagelevels and/or current levels at monitored devices, value of meters,power usage by individual devices, etc. Routine message traffic may bescheduled to occur at certain intervals. Examples are network status,device status, abnormal line voltage, power quality, tilt sensor toalert of pole failure, air quality, road conditions, for example,monitored by a video camera linked into the network, et cetera. Theperiod of these. reporting intervals is programmable (e.g., fromone-hour to 24-hour intervals in 15 minute increments or less). Event oralarm reporting may be handled on a priority basis, and it does notconform to a routine forwarding schedule.

In an example embodiment, when the alarm data is received at networkoperation center 106, it is compared to predetermined action stored in aprogram, and the actions are carried out as described. For example, thenetwork operation center may send an email to certain individuals, a mapshowing the location of the failed device, and/or generate a work orderby interfacing with a subscriber/customer's work-order program.

The type of data sent from network operations center 106 to asubscriber/customer is not limited, but in practical terms may belimited in its usefulness to a subscriber/customer based on ability toreceive and use the data.

In an example embodiment, the message traffic passed between networkoperation center 106 and intelligent luminaire managers 112 includesapplications data packages, query command packages, device statuspackages, event and alarm packages, and network status packages.

Subscriber/customer access to this data stored at the network operationcenter is controlled by password. Subscriber/customer notification ofevents is transmitted to the subscriber/customer, and no password isrequired to obtain this data.

In an example embodiment, network operation center 106 is able toidentify when there is a power failure effecting a subscriber/customer'slight system and when backup power is being used at master controls 114.For a system-wide power outage, network operation center 106 canconsolidate alarm reports and generate a generalized message that isforwarded to an effected subscriber/customer (e.g., a light-systemowner/operator 108).

As noted above, in the event of a power failure or a network failuresuch that a master controller 114 cannot provide data to networkoperation center 106 on a scheduled interval, the data is maintained atthe master controller 114 until power and communications are restored.The stored data is then forwarded at the next scheduled reportinginterval, unless specifically requested earlier by asubscriber/customer. In an example embodiment, master controller 114includes battery back-up power. In another embodiment, master controller114 is capable of transmitting an “I've Lost Power” signal when power islost.

Network operation center 106 is responsible for IP protocol trafficanalysis. Traffic is routed such that it is able to support peak loadingof the data network and still pass data. In order to manage data,subscriber/customer commands may be limited during certain unexpectedpeak loads and held until bandwidth becomes available to forward thistraffic. When a bandwidth limitation is being reached in a network 102,an alarm is sent to network operation center 106 so that traffic can bemanaged accordingly to control the peak load. Network operation center106 personnel can monitor traffic loading on the network and installadditional capacity as required.

In an embodiment, as noted above, network operation center personnelperform asset management functions, which include tracking the lifecycle of node equipment, and replacing end-of-life equipment or degradedequipment before failure. For light system owner/operators 108, networkoperation center 106 data analysis programs can track the complete lifeof a device (e.g., the time it was installed, the number of hours it wasoperated, and a cause of failure).

Network security services 412 control access to the information storedby network operation center 106 using firewalls and prevent unauthorizedaccess/network usage to prevent compromise of the data and/or network.In an example embodiment, network security services 412 may require bothauthentication and authorization. Security techniques may be implementedto prevent denial-of-service attacks and virus attacks that would causethe networks to fail or breakdown. Network security services 412 mayalso include intrusion tracking and the ability to trace and combatmalicious acts by unauthorized users. In an example embodiment, a “callhome” feature is used such that when a request for information orservice is sent from a subscriber/customer to network operation center106, the request is repeated and sent back to the subscriber/customer'sknown address by network operation center 106 to verify that the requestactually came from that subscriber/customer. Network security services412 may also employ and support data encryption.

In an embodiment, network operation center 106 as a part of itssubscriber/customer service provides monthly reports summarizing assetstatus of monitored devices to subscribers/customers.

Additionally, in an embodiment, network operation center 106 sendsmessages to light system managers when a light is turned on and when itis turned off so that the light system manager can keep track of thepresent status of the light system assets.

FIG. 4B illustrates another embodiment of a network operation centeraccording to the present invention. As shown in FIG. 4B, all thefunctions and functionality of network operation center 106 describedabove need not reside at a single geographical location. Thisfunctionality can be distributed over a wide geographical area. As shownin FIG. 4B, in an embodiment, the functionality of network operationcenter 106 is distributed across a central network operation center(NOC) 420 and one or more regional/customer network operation centers422.

FIG. 5A depicts a light system owner/operator 108. As shown in FIG. 5A,owner/operator 108 may be divided into a light system manager portion109 and a maintenance unit portion 111. The light system manager portionmay include a subscriber server 500, a database 502, and a computerdisplay 504.

Computer display 504 may present, in both a text and a graphical manner,information about the owner/operator's light system. The text andgraphical information includes, for example, the status of any alarms,power usage, network status, and device status. The status may also beshown graphically on a visual map display. In an example embodiment, agraphical user interface presents a visual photometric mapping to auser, for example, of selected lights of the light system. Thisphotometric mapping can provide the user with a visual representation ofthe illumination, for example, of a parking lot, a sports field, orother area of interest. The bottom portion of computer screen 504 showscommands being entered and responses being received from networkoperation center 106.

The light system manager may have the ability to run several programs athis or her site. These programs may include alarm and maintenance (e.g.,repair dispatch) program(s) 506, light system management program(s) 508,billing program(s) 510, data analysis program(s) 512, a data storage andretrieval program 514, a network operation center interface program 516,and a data routing program 518. Each of these programs is furtherdescribed below.

Alarm and maintenance program(s) 506 displays an alarm such thatmaintenance personnel 120 can take corrective action. In an embodiment,the program uses data that has been analyzed, for example, by networkoperation center 106 and schedules maintenance so that equipment in thefield close to the end of its useful operating life can be replacedprior to failure. For predictability, this end of life analysis can bebased on a larger population of equipment than only that owned andoperated by a particular light system manager.

Light management program(s) 508 are used by the light system manager toreprogram devices in the field. Examples of this include, for example,turning lights on and lights off using a schedule rather than havingthem simply turn on at dusk and off at dawn.

Billing program(s) 510 keep track of when specific lights are used andgenerates customer bills accordingly. In an example embodiment, the ratecharged for turning on and using a particular light can be based on thetime it is turned on (e.g., during peak hours of operation or off-peakhours of operation).

Data analysis program(s) 512 maintain the state of components in use ina light system and compare, for example, each component's total time inuse to an estimated life expectancy to predict a remaining time tofailure for the component. When a component is at its expected end oflife, the data generated by program(s) 512 can be used to create a workorder to have maintenance personnel 120 replace the component before itfails, for example, by interacting with a maintenance/work order program520.

Data storage and retrieval program(s) 514 facilitate the storage andretrieval of data at the light manager's site in database 502.

Network operating system interface program 516 is used to interface withnetwork operation center 106. This interface program is useful, forexample, for transmitting data to and receiving data from intelligentluminaire managers 112 installed on the light system manager'sequipment.

Data routing program 518 parses and routes data received from networkoperation center 106.

On the maintenance unit side, there may be included a maintenance workorder program 520, an intelligent luminaire manager field unit interfacedevice 522, and an intelligent luminaire manager field unit 524. Alsoincluded may be an inventory purchasing program 526 and an assetmanagement program 528.

In an example embodiment, when an alarm or maintenance requirement issent to the light system manager by network operation center 106, it maybe automatically routed to maintenance/work order program 520. Thisprogram then automatically generates a work order that can be acted uponby a maintenance worker. An electronic copy of the work order can bedownloaded to intelligent luminaire manager field unit 524 viaintelligent luminaire manager field unit interface 522.

In an example embodiment, intelligent luminaire manager field unit 524may be a hand-carried portable device that can be taken on-site whileinstalling and/or servicing a luminaire 200. Information about theinstallation and/or service is captured by intelligent luminaire managerfield unit 524 for subsequent entry into the records of the networkoperation center 106 or the light system owner/operator 108. Upon returnof the maintenance worker to the maintenance unit, the collectedinformation may be uploaded from the field unit into maintenancerecords. In an embodiment, this uploaded information may be forwarded tonetwork operation center 106 where it is stored and analyzed along withinformation gathered by maintenance units of other light systemowner/operators.

In an embodiment, alarms generated by an intelligent luminaire manager112 are not cleared until replacement/service information is received atnetwork operation center 106.

In an embodiment, inventory purchasing program 526 keeps track, forexample, of stock on hand and causes equipment to be ordered and stockedbased on information collected from intelligent luminaire managers 112.

The asset management program 528 is a program that modifies assetmanagement data received, for example, from network operation center 106to satisfy particular light system owner/operator data requirements.

Based on the description contained herein, it will be appreciated thatany or all of the functions and/or functionality described with regardsto network operation center 166 can be implemented, for example, by alight system owner/operator 108. Similarly, any or all of the functionsand/or functionality described with respect to a light systemowner/operator can be implemented by network operation center 106. Thus,the illustration and description of specific functions and functionalityresiding at a particular location or with a particular entity isillustrative and not intended to limit embodiments of the invention.

FIG. 5B further illustrates intelligent luminaire manager field unit524. Field unit 524 is used, for example, to activate newly installed orserviced intelligent luminaire managers 112.

In an example embodiment, field unit 524 may include an on-board GPSsystem 534 and a communications interface 536. The communicationsinterface can communicate, for example, with an intelligent luminairemanager 112 or other device using RF and/or optical communications.

Using the GPS system 534, the field unit 524 may identify the locationwhere an intelligent luminaire manager 112 is installed. This locationinformation may be stored, for example, in memory 320 of intelligentluminaire manager 112. The location information for the installation mayalso be recorded in the field unit 524, which may be taken back to themaintenance unit and stored in the maintenance unit's records.Alternatively, the location information for the installation may beforwarded to network operation center 106 via the light manager'ssubscriber/customer interface to network operation center 106.

Other information collected during the installation may include, forexample, all the particulars about the equipment monitored andcontrolled by the intelligent luminaire manager 112 (e.g., lamp type,ballast type, digital photo, etc.). As an example, the lamp type andelectrical specifications associated therewith (e.g., voltage andcurrent parameters) may be captured during installation. In an exampleembodiment, the field unit 524 may include a bar code reader forcapturing the additional information that may be stored in a bar codeassociated with the intelligent luminaire manager 112 or equipmentassociated therewith. The additional information captured by the fieldunit 524 may then be later provided for subsequent entry into therecords of the network operation center 106 or the light systemowner/operator 108. Alternatively, the additional information may beforwarded to network operation center 106 via the light manager'ssubscriber/customer interface to network operation center 106.

In example embodiments of the invention, for example where more than oneintelligent luminaire manager 112 may be installed at the samegeographical location (e.g., in a situation where two luminaires areattached to a single pole and each luminaire has its own intelligentluminaire manager 112), field unit 524 can be used to assign a uniqueidentification value to each of the luminaire managers.

Once an intelligent luminaire manager 112 is installed, itself-configures by running a configuration program. Once alive, network102 notifies network operation center 106, via master controller 114,that a new device has entered the network.

In an example embodiment, field unit 524 is hosted by a PDA 530, runningapplication program(s) 532. Embodiments of the invention are notlimited, however, to requiring the use of a PDA. Map base reportsdownloaded to field unit 524 show the location of each luminaire in alight system and display efficient driving routes for maintenance crewsto get to a luminaire requiring repair. Fault types are communicated tocrews via network operation center 106 and field unit 524 forpre-diagnostics of a failed luminaire so that time on-site is minimizedand the need for return trips to a failed luminaire are eliminated. Inan embodiment, the type of faults and corrective actions that can beprovided to maintenance crew workers include anticipated lamp cycling,lamp cycling, no starting pulse, starting pulse but failed to start,non-reporting unit, replace lamp when traveling to area, replace lamp,replace starter, check power at fixture, if no power repair power, andif power replace intelligent luminaire manager unit. It will beappreciated this list is illustrative and not intended to limitembodiments of the invention.

During activation of a new intelligent luminaire manager 112, each unitmay be identified both in terms of its type of luminaire and its GPSlocation. This data, coupled with the failure mode reporting, allows fora much greater maintenance crew efficiency. Additionally, dedicated,less-costly maintenance crews are able to conduct all maintenance duringdaylight hours, rather than nighttime, at significantly lower cost.

In an example embodiment, when an intelligent luminaire manager 112 isremoved from service, its identification number may be captured by fieldunit 524. If the GPS coordinates of the removed intelligent luminairemanager 112 differ from what is expected (e.g., by more than a couple ofmeters) an alert/alarm may be generated or initiated by field unit 524and may be provided to network operation center 106. The alarm may be anindication, for example, that (1) the removed intelligent luminairemanager 112 was originally installed improperly (e.g., at the wronglocation or with the wrong GPS coordinates); (2) the removed intelligentluminaire manager 112 has been moved since its activation without properauthority; or (3) the data stored by the removed intelligent luminairemanager 112 has been corrupted.

According to an example embodiment of the invention, diagnostics such asbad fixture detection and cycling may be performed locally at anintelligent luminaire manager 112. FIG. 6 is a flow chart illustratingthe blocks of a diagnostic method 600 for determining a bad fixture,according to an example embodiment of the invention. The diagnosticmethod 600 may be implemented by embodiments of an intelligent luminairemanager 112. In an example embodiment of the invention, the diagnosticmethod 600 may operate during an initial start-up phase for a luminaire,according to an example embodiment of the invention.

In block 602, a controller of an intelligent luminaire manager 112 mayinitially direct that an associated luminaire be provided in an ONstate. Accordingly, the controller may provide a directive to close arelay for supplying power to the luminaire. Assuming that the fixture isnot bad, the closing of a relay typically results in power beingprovided to a luminaire, and the luminaire turns on. In block 604, theintelligent luminaire manager 112 may clear any alarms or other flagsthat are otherwise stored in its memory. In block 606, the intelligentluminaire manager 112 may wait for a predetermined delay period T₁ afterdirecting that the relay be closed before proceeding with block 608. Inan example embodiment of the invention, the delay period T₁ may be 10seconds, although a shorter or longer time period T₁ may also beutilized without departing from example embodiments of the invention.Following the delay period T₁, processing proceeds to block 608.

In block 608, the luminaire diagnostics program stored in the memory ofthe controller may access voltage information from a voltage sensor andcurrent information from a current sensor. The voltage information maybe based upon the voltage sensor measuring a voltage provided to aluminaire. The current information may be based upon the current sensormeasuring a current provided to the luminaire. The luminaire diagnosticsprogram may calculate the real power using the voltage information andthe current information. In an example embodiment of the invention, thereal power may be calculated a number of instances over a time period inorder to compute an average real power P for the time period. Forexample, the real power may be calculated once per second for a total of8 seconds, and the 8 calculated values of the real power may be averagedto provide an average real power P for the past 8 seconds. It will beappreciated that the frequency at which the real power is calculated maybe adjusted without departing from example embodiments of the invention.Likewise, the number of real power values included in the average realpower P computation may likewise be adjusted without departing fromexample embodiments of the invention.

In block 610, the average real power P calculated in block 608 that wasdetermined shortly after directing that the relay be closed may be savedfor later use as the initial Power P₁. In block 612, an average realpower P for a subsequent time period may be calculated. For example,similar to the calculation in block 608, the real power may becalculated once per second for a total of 8 seconds, and the 8calculated values of the real power may be averaged to provide anaverage real power P for the past 8 seconds. It will be appreciated thatthe frequency in which the real power is calculated and the number ofreal power values included in the average real power P computation maybe varied in accordance with example embodiments of the invention.

Following block 612, processing may proceed to block 614. In block 614,the present average real power P is compared to a bad fixture threshold.In an example embodiment of the invention, the bad-fixture threshold maybe set at around 70W; however, the bad fixture threshold may be setdepending on the type of luminaire installed. In an example embodimentof the invention, the bad fixture threshold may be set at a real powerlevel that would be indicative of a bad fixture. Accordingly, block 614may determine whether the present average real power P is greater thanthe bad-fixture threshold (e.g., 70W). It will be appreciated that whilea luminaire (e.g., having a high-intensity discharge (HID) lamp) isstill in a start-up process, there may not necessarily be a bad fixtureeven if the present average real power P is less than the bad-fixturethreshold. Thus, block 614 also determines whether the present averagereal power P is still increasing. As an example, block 614 may determinewhether the magnitude between the present average real power P and theinitial Power P_(i) is greater than a particular power threshold (e.g.,10% of the initial Power P_(i)).

If block 614 determines that the current average real power P is greaterthan the bad-fixture threshold (e.g., 70W) and the magnitude between thepresent average real power P and the initial Power P_(i) is greater thana particular power threshold (e.g., 10% of the initial power P_(i)),then there may not be any bad fixture determined by diagnostic method600. On the other hand, if either the average real power P is greaterthan the bad-fixture threshold (e.g., 70W) or the magnitude between theaverage real power P and the initial Power P_(i) is less than aparticular power threshold (e.g., 10% or another percentage of theinitial power P_(i)), then processing may proceed to block 616.

Block 616 may also determine whether a second delay period T₂ (e.g., 10minutes) has elapsed since the controller directed that the relay beclosed to supply power to the luminaire. It will be appreciated that thesecond delay period T₂ may be set at 10 minutes or another time periodthat is sufficient for determining whether or not the fixture is a badfixture, according to an example embodiment of the invention. If block616 determines that the second delay period T₂ has not elapsed, thenprocessing may return to blocks 612 and 614 to determine whether thebad-fixture threshold or power threshold are now met. On the other hand,if block 616 determines that the second time period has elapsed, thenprocessing may proceed to block 618. Block 618 may determine whether thepresent average real power P is greater than the bad-fixture threshold(e.g., 70W). If so, then block 622 may determine that there is a Non-HIDlamp installed, and a “Non-HID Lamp” alarm or flag may be set. On theother hand, if block 618 determines that the present average real powerP is less than the bad-fixture threshold (e.g., 70W), then processingmay proceed to block 620. In block 620, a “bad fixture” alarm or flagmay be set. The alarm or flag that is set in block 620 or 622 may betransmitted in a message by an intelligent luminaire manager 112 vianetwork 102 to the network operation center 106. The network operationcenter 106 may provide the received alarm, flag, or other statusinformation to the light system owner/operators 108 and/or maintenancepersonnel.

FIG. 7 is a flow chart illustrating the blocks of a diagnostic method700 for determining cycling of a luminaire, according to an exampleembodiment of the invention. The diagnostic method 700 may beimplemented by embodiments of an intelligent luminaire manager 112. Inan example embodiment of the invention, the diagnostic method 700 may beutilized following a predetermined delay after directing the closure ofthe relay or following the operation of the diagnostic method 600 ofFIG. 6.

In block 702, a luminaire diagnostics program stored in a memory of thecontroller of an intelligent luminaire manager 112 may initialize (e.g.,set to zero) or reset a reference power P_(REF) value stored in amemory. In block 704, the luminaire diagnostics program may access orreceive voltage information from a voltage sensor and currentinformation from a current sensor. The luminaire diagnostics program maycalculate the current power P, using the voltage information and currentinformation. In block 706, the luminaire diagnostics program mayincrement a Power Counter that is stored in the memory. The PowerCounter may be utilized by the luminaire diagnostics program todetermine when to calculate an average power P_(AVG) for use inadjusting a value of the reference power P_(REF) value.

Block 708 may determine whether the Power Counter has reached apredetermined value (e.g., Power_Counter=8?). If so, then processing mayproceed to block 710. In block 710, the luminaire diagnostic program maydetermine the current average power P_(AVG.) In addition, in block 710,the Power Counter may be reset. In block 712, the luminaire diagnosticprogram may determine whether the current average power P_(AVG) isgreater than the reference power P_(REF) value. If so, then processingmay proceed to block 714, where the reference power P_(REF) value may beset to be the current average power P_(AVG) computed in block 710. Thenew reference power P_(REF) value may then be utilized in the comparisonof block 716.

In block 716, the luminaire diagnostic program may make a determinationas to whether the current power P, value is less than a predeterminedamount (e.g., 50%, a range of between 40%-60%, etc.) of the referencepower P_(REF) value or another threshold value. If block 716 determinesthat the current power P, value is greater than a predetermined amount(e.g., 50%) of the reference power P_(REF) value or other thresholdvalue, then processing may return to block 704. On the other hand, ifblock 716 determines that the current power P_(i) value does not exceeda predetermined amount (e.g., 50%) of the reference power P_(REF) valueor other threshold value, then processing may proceed to block 718. Inblock 718, the luminaire diagnostic program may increment a cyclingcondition counter that indicates that a potential cycling fault has beendetected. It will be appreciated the cycling condition counter may havebeen incremented each time that the diagnostic method 700 has detected acycling condition. Once the cycling condition counter has reached one ormore thresholds within a time period, then an actual alarm or flag maybe set in a memory by the luminaire diagnostic program, and a cyclingevent may also be transmitted in message by intelligent luminairemanager 112 via network 112 to the network operation center 106. Forexample, in block 720 if the cycling condition counter reaches a firstpredetermined threshold (e.g., 5), then processing proceeds to block721, where a “Cycling Lamp” alarm or flag is set, and a cycling eventindicating a cycling fault may be transmitted via network 112 to thenetwork operation center 106. In addition, if the cycling conditioncounter reaches a second predetermined threshold (e.g., 10) in block722, then processing may proceed to block 721, and another eventindicating a cycling fault may be transmitted via network 112 to thenetwork operation center 106. Further, if the counter reaches a thirdpredetermined threshold (e.g., 25) in block 724, then processing mayproceed to block 721, and another event indicating a cycling fault maybe transmitted to the network operation center 106 via the network 102.The network operation center 106 may provide the received alarm, flag,or other status information to the light system owner/operators 108and/or maintenance personnel. It will also be appreciated that a networkowner may determine the threshold number of cycling condition countsthat must be accumulated before a “cycling lamp” alarm or flag is set oran event is transmitted via network 112 to the network operation center106. For example, one network owner may not be concerned with less than10 cycles in a 24-hour period, while another network owner may find that5 cycles in a 24-hour period is unacceptable. Accordingly, one or moreof blocks 720/721, 722/723, and 724/725 may not necessarily be availablein accordance with other example embodiments of the invention. Manyvariations of these thresholds are available in accordance with exampleembodiments of the invention. Following blocks 721, 723, and 725,processing may proceed to block 726, where a certain delay period (e.g.,1200 seconds) may be implemented before the diagnostic method 700attempts to identify additional cycling conditions of the luminaire.

FIG. 8A is a flow chart illustrating the blocks of a diagnostic method800 for a wire check algorithm, according to an example embodiment ofthe invention. The diagnostic method 800 may be implemented byembodiments of an intelligent luminaire manager 112. The diagnosticmethod 800 may be performed by the intelligent luminaire manager 112based upon a input line voltage V_(LINE), a measured output load voltageV_(LOAD) associated with a luminaire, and a power P being drawn by theluminaire. It will be appreciated that the input line voltage V_(LINE)and the load voltage V_(LOAD) may be received by the intelligentluminaire manager 112 from voltage sensors, according to an exampleembodiment of the invention. For example, load voltage V_(LOAD) may bedetermined by a voltage sensor measuring a voltage from a load leg of aluminaire to neutral. Alternatively, the load voltage load voltageV_(LOAD) may be determined by a voltage sensor measuring a voltageacross the relay the supplies power to the luminaire. In addition, theintelligent luminaire manager 112 may determine a current (I) beingprovided to a luminaire, and the power P being drawn by the luminairemay be computed, according to an example embodiment of the invention. Inan example embodiment of the invention, every time when V_(LINE),V_(LOAD), I is read, and P is computed, the diagnostic method 800 may beperformed by the luminaire diagnostics program of the intelligentluminaire manager 112, except perhaps after a predetermined amount oftime (e.g., 10 seconds) after the relay is directed to change states.

Block 802 may determine whether the luminaire is expected to be in anOFF command state. In an example embodiment of the invention, theintelligent luminaire manager 112 may determine whether the luminaire isexpected to be in an OFF command state based upon information receivedfrom a photo-detector or other photocell device. In an exampleembodiment of the invention, if a threshold level of daylight isdetected by the photo-detector or photocell device, then the intelligentluminaire manager 112 may determine that the luminaire is expected to bein an OFF command state.

If the luminaire is not expected to be in an OFF command state in block802—that is, the luminaire is expected to be in an ON command state,then processing may proceed to block 804. Block 804 may determinewhether not substantially equal voltages are detected between the linevoltage V_(LINE) and the load voltage V_(LOAD). Indeed, substantiallyequal voltages between the line voltage V_(LINE) and the load voltageV_(LOAD) may be expected when the luminaire is actually ON. For example,block 804 may include determining whether a magnitude of the differencebetween the V_(LOAD) and V_(LINE) is greater than a threshold value. Asan example, the threshold value may be set as a percentage (e.g., 12.5%)of the line voltage V_(LINE). If block 802 determines that the linevoltage V_(LINE) is not substantially equal to the load voltageV_(LOAD), then processing may proceed to block 806, where the relay isdetermined to be open. Otherwise, block 804 may finish without any errorstate being detected.

On the other hand, if the luminaire is expected to be in an OFF commandstate in block 802, then processing may proceed to block 808. Block 808may determine whether substantially unequal voltages are detectedbetween the line voltage V_(LINE) and the load voltage V_(LOAD). Indeed,substantially unequal voltages between the line voltage V_(LINE) and theload voltage V_(LOAD) may be expected when the luminaire is actuallyOFF. For example, block 804 may include determining whether a magnitudeof the difference between the load voltage V_(LOAD) and the line voltageV_(LINE) is less than a threshold value. As an example, the thresholdvalue may be set as a percentage (e.g., 12.5%) of the line voltageV_(LINE).

If block 808 determines that substantially unequal voltages are detectedbetween the line voltage V_(LINE) and the load voltage V_(LOAD), then apotential condition may be present, and processing may proceed to block810. Block 810 may determine whether the power P drawn by the luminaireis less than a threshold amount (e.g., 5W). If the power P drawn by theluminaire is less than a threshold amount, then processing may proceedto block 814, where a miswiring condition #1 is detected, as illustratedby FIG. 8B. With the miswiring condition #1, the luminaire may beconnected to power supply line L2 instead of the Neutral N. On the otherhand, if the power P drawn by the luminaire is greater than thethreshold amount, then processing may proceed to block 812, where awelded relay condition is determined. A welded relay condition mayresult in the relay remaining closed even when instructed to open.

On the other hand, block 808 may determine that substantially unequalvoltages are not detected between the line voltage V_(LINE) and the loadvoltage V_(LOAD). In this case, processing may proceed to block 816.Block 816 may include determining whether the load voltage V_(LOAD) isgreater than a threshold amount (e.g., 5V) for a predetermined number ofreadings (e.g., 8 consecutive readings over a predetermined period oftime). If not, then a potential condition may be present and processingmay proceed to block 818. Block 818 may determine whether the loadvoltage V_(LOAD) exceeds a predetermined amount (e.g., 112.5%) of theline voltage V_(LOAD) or another threshold amount. If not, thenmiswiring condition #2 is detected in block 820, as illustrated in FIG.8B. Otherwise, miswiring condition #3 is detected in block 822, as alsoillustrated in FIG. 8B. With miswiring condition #2, the intelligentluminaire manager 112 may be connected to the second power supply lineL2 instead of neutral. With miswiring condition #3, the luminaire may beconnected to the second supply line L2 instead of neutral N. Inaddition, the installed positions of the neutral N and first powersupply line L1 for the intelligent luminaire manager 112 may be swapped.According to an example embodiment of the invention, the detectedconditions in blocks 806, 812, 814, 820, and/or 822, or other detectedstatus, may be transmitted in a message by an intelligent luminairemanager 112 to the network operation center 106 via network 102.

It will be appreciated that the diagnostic methods disclosed in FIGS. 6,7, and 8A-B have been provided for illustrative purposes and that otherdiagnostic methods may be provided by the intelligent luminaire manager112.

As an example, another diagnostic method may include determininghigh-current levels or low-current levels being provided or drawn by aluminaire or other device. High-current levels may be indicative ofequipment malfunction such as a malfunction with a ballast. In anexample embodiment, a current sensor may provide the intelligentluminaire manager 112 with information regarding current levels (e.g.,instantaneous current level, averaged current level) being provided ordrawn by the luminaire or other device (e.g., a load current). Thecurrent level may then be compared to one or more thresholds, which mayinclude a nominal expected current level (e.g., 10A), a maximum currentlevel (e.g., 15A), a low current level (e.g., 5A), or another desiredcurrent threshold. If the current level exceeds one or more thresholdvalues, then the intelligent luminaire manager 112 may generate ahigh-current alarm event or status. If the instantaneous current levelis lower than one or more threshold values, then the intelligentluminaire manager 112 may generate a low-current alarm event or status.The generated alarm event or status may be transmitted to the networkoperation center 106 via the network 102. The network operation center106 may provide the received alarm event or status information to thelight system owner/operators 108 and/or maintenance personnel.

It will also be appreciated that while FIGS. 6, 7, and 8A-B havedescribed diagnostic methods that may be performed by an intelligentluminaire manager 112, other diagnostic methods may be performed at asystem-level. Indeed, system-level diagnostics such as fixturemalfunction or day burning can also be performed remotely at a networkoperation center 106 based upon (i) operational and/or event informationreceived from an intelligent luminaire manager 112 and (ii) activationinformation or other operational information acquired duringinstallation of an intelligent luminaire manager 112 or associatedequipment/fixture/luminaire, perhaps received from a field unit 122,524. Examples of operational information received by the networkoperation center 106 from an intelligent luminaire manager 112 mayinclude information, perhaps transmitted periodically (e.g., hourly) orin conjunction with one or more reported events, relating to supplied orutilized current (I) and voltage (V) information associated withoperation of the luminaire. Examples of activation information mayinclude the type/identification of the lamp installed in the luminaire(e.g., HID lamp, non-HID lamp, LED lamp), the luminaire itself, andoperating specifications associated with the installed luminaire,including power, current, and/or voltage specifications. The activationinformation may be obtained using a PDA-hosted field unit, as describedherein. If the activation information specifies the type/identificationof the installed luminaire, but perhaps not the actual desired operatingspecification, then the network operation center 106 may use thetype/identification information to determine the desired operatingspecification (e.g., perhaps provided by the manufacturer or anothersource) associated therewith.

It will be appreciated that the network operation center 106 may receiveand store operational information received from the intelligentluminaire managers 112. The storage of the operational information atthe network operation center 106 may reduce the amount of data thatneeds to be stored by the intelligent luminaire manager 112, accordingto example embodiment of the invention. In addition, the storedhistorical operational information may be utilized by the networkoperation center 106 in performing additional diagnostics or analyses.

FIG. 9 is a flow chart illustrating the blocks of a diagnostic method900 for determining a fixture malfunction, according to an exampleembodiment of the invention. The diagnostic method 900 may beimplemented by embodiments of a network operation center 106. In block902, a fixture malfunction counter may be reset (e.g., set to zero). Thefixture malfunction counter may generally track a number of possibledetected fixture malfunction incidents during a period of time. Thefixture malfunction counter may be reset periodically, in accordancewith a schedule, or on request. In block 904, the network operationcenter 106 may receive operational information from an intelligentluminaire manager 112 or other RF device, including informationregarding current, voltage, and/or power levels drawn by or suppliedduring operation of the luminaire or other equipment.

In block 906, at least a portion of the received operational informationmay be compared to one or more predetermined thresholds. In an exampleembodiment of the invention, the one or more predetermined thresholdsmay be based upon activation information obtained during installationand activation of an intelligent luminaire manager 112 or other RFdevice. Indeed, a maintenance worker may store the activationinformation in the handheld unit 122, 524 for subsequent delivery to andstorage at the network operation center 106. For example, a maintenanceworker may be manually enter the information into the handheld unit 122,524, or perhaps otherwise provide the information to the handheld unit122, 524 by scanning a bar code either on the installed equipment (e.g.,a luminaire) or elsewhere to identify the installed equipment or aspecification associated with the installed equipment. Alternatively,the activation information may be transmitted in a message from theintelligent luminaire manager 112 or other RF device to the to thenetwork operation center 106 via the network 102.

In an example embodiment of the invention, the activation informationmay specify a type or identification of an installed luminaire or otherequipment. The activation information may also include electricalspecifications, including expected operating specifications (e.g.,power, current, and/or voltage operating specifications) of theinstalled luminaire or other equipment. Alternatively, if the activationinformation a type or identification of an installed luminaire or otherequipment, the network operation center 106 may be able to determine theassociated operating specifications (e.g., electrical specifications),perhaps based upon manufacturer specifications or ANSI specifications.

As introduced above, in block 906, at least a portion of the receivedoperational information may be compared to one or more predeterminedthresholds that may be determined based upon the activation information.It will also be appreciated that the one or more predeterminedthresholds may vary depending on whether the luminaire or otherequipment is operating in an ON or OFF command state. In an exampleembodiment of the invention, received power information associated withoperation of the installed luminaire or other equipment may be comparedto the expected power operating specification based upon the receivedactivation information. In another example embodiment, the receivedcurrent or voltage information may be compared to the expected currentor voltage operating specifications based upon the received activationinformation.

In block 908, the network operation center 106 may determine whether oneor more operating specifications or thresholds in block 906 have beenexceeded (or exceeded by an impermissible threshold amount orpercentage). If one or more operating specifications or thresholds havebeen exceeded, then the luminaire may be operating out ofspecifications, and processing may proceed to block 910. In block 910,the fixture malfunction counter may be incremented to signify that apotential fixture malfunction incident has been detected.

In block 912, if the fixture malfunction counter is greater than athreshold amount within a time period, then processing may proceed toblock 914. It will be appreciated that the threshold amount in block 912may be set based upon input from the light system owner/operators 108 oranother entity. In block 914, the network operation center 106 maydetermine that there is a fixture malfunction or other operationalstatus. The network operation center 106 may then generate an equipmentstatus based at least in part on the determined fixture malfunction orother operational status. The system owner/operators 108 and/ormaintenance personnel may be notified of the fixture malfunction orother operational status, as described herein. In an example embodimentof the invention, the determined fixture malfunction or otheroperational status may be included in a work order report, as alsodescribed herein.

According to an example embodiment of the invention, the diagnosticsmethod 900 may be utilized to determine excessive power consumption by aluminaire or other device. For example, the network operation center 106may receive operational information from the intelligent luminairemanager 112 or other RF device, including current, voltage, and/or powerlevel information associated with the luminaire. The network operationcenter 106 may determine the power consumption associated with theluminaire or other device and compare the power consumption to nominalexpected power level for the luminaire or other device plus a thresholdvalue. If the power consumption associated with the luminaire or otherdevice exceeds the nominal expected power levels plus the thresholdvalue, then the network operation center 106 may determine anoperational status associated with excessive power consumption. Thenetwork operation center 106 may then generate an indication or othermessage identifying the excessive power consumption. Indeed, the systemowner/operators 108 and/or maintenance personnel may be notified of theexcessive power consumption, as described herein. In an exampleembodiment of the invention, the determined excessive power consumptionsstatus of the luminaire may be included in a work order report, as alsodescribed herein.

FIG. 10 is a flow chart illustrating the blocks of a diagnostic method1000 for determining a dayburning malfunction, according to an exampleembodiment of the invention. The diagnostic method 1000 may beimplemented by embodiments of a network operation center 106.

In block 1002, a dayburning counter may be reset (e.g., set to zero).The dayburning counter may generally track a number of possible detecteddayburning incidents during a period of time. The dayburning counter maybe reset periodically or in accordance with a schedule. In block 1004,the network operation center 106 may receive operational informationfrom an intelligent luminaire manager 112, including informationregarding current, voltage, and/or power levels drawn by or otherwiseassociated with operation of the luminaire.

In block 1006, the network operation center 106 may determine whetherthe received operational information indicates that intelligentluminaire manager 112 is operating in an OFF state. If so, then theluminaire is likewise expected to be off, and the network operationcenter 106 may proceed to block 1008 to determine whether a dayburningcondition associated with the luminaire is present. According to anexample embodiment, block 1008 may determine whether the luminaire isstill drawing more than an insignificant power level when theintelligent luminaire manager 112 is operating in an OFF state.Accordingly, block 1008 may include determining whether the power leveldrawn by the luminaire exceeds a maximum threshold amount (e.g., athreshold between 0W-2W). The maximum threshold amount may be adjustedin accordance with an example embodiment of the invention

If block 1008 determines that the luminaire is still drawing more thanan insignificant power level when the intelligent luminaire manager 112is operating in an OFF state, then processing may proceed to block 1010.In block 1010, the dayburning counter may be incremented to signify thata potential dayburning incident has been detected.

In block 1012, if the dayburning counter is greater than a thresholdamount within a time period, then processing may proceed to block 1014.The threshold amount in block 1012 may be set based upon input from thelight system owner/operators 108 or another entity. In block 1014, thenetwork operation center 106 may determine that there is a dayburningmalfunction. The system owner/operators 108 and/or maintenance personnelmay be notified of the dayburning malfunction, as described herein. Inan example embodiment of the invention, the determined dayburningmalfunction may be included in a work order report, as also describedherein.

It will be appreciated that system-level diagnostics at the networkoperation center 106 may also utilize system-level information inperforming the diagnostics. For example, information received fromadjacent intelligent luminaire managers 112 or RF devices may beutilized to determine whether a condition detected by a particularintelligent luminaire manager 112 or RF device is the result of a localproblem, or whether there is a system-level problem such as a blackoutor a power transmission quality issue.

In an example embodiment of the invention, the network operation center106 may also diagnose communication problems associated with theintelligent luminaire manager 112 or other RF device. According to anexample embodiment of the invention, the network operation center 106may expect to receive periodic reports, messages, or events/alarms froman intelligent luminaire manager 112 or other RF device. For example,during normal operation, the intelligent luminaire manager 112 or otherRF device may transmit periodic reports with voltage and currentinformation associated with the monitored equipment to the networkoperation center 106. Likewise, the intelligent luminaire manager 112 orother RF device may likewise transmit messages to the network operationcenter 106 when there is a change in operational state (e.g., ON, OFF,etc.) or other status. Similarly, an alarm or event may be transmittedfrom the intelligent luminaire manager 112 or other RF device to thenetwork operation center on a priority basis as well. Accordingly, thenetwork operation center 106 may determine that an intelligent luminairemanager 112 or other RF device is experiencing a communication problemwhere the network operation center 106 does not receive anycommunication (e.g., periodic reports, status messages, events/alarms,etc.) from the intelligent luminaire manager 112 or other RF device fora predetermined period of time (e.g., 2 days, 4 days, etc.). In anexample embodiment of the invention, the lack of communications from anintelligent luminaire manager 112 or other RF device may be classified,prioritized, or grouped by the network operation center 106 according toduration of the lack of communications. For example, low-priorityno-communication problems may be associated with a lack ofcommunications for less than 24 hours. Medium-priority communicationproblems may be associated with lack of communications for between 24hours and 48 hours. High-priority communication problems may beassociated with lack of communications for over 48 hours. Manyvariations in the classifications, prioritizations, and grouping may beavailable in accordance with example embodiments of the invention.System owner/operators 108 and/or maintenance personnel may be notifiedof some or all of the communication problems.

According to another example embodiment, the network operation center106 may also diagnose system-level communication problems associatedwith a plurality of intelligent luminaire managers 112 or other RFdevices. In an example embodiment of the invention, the networkoperation center 106 may initially determine individual communicationproblems for a plurality of intelligent luminaire managers 112 or otherRF devices, as described above. The network operation center 106 canthen analyze the plurality of intelligent luminaire managers 112 or RFdevices having communication problems to determine whether asystem-level problem can be determined. Examples of system-levelproblems may include network system failures or power distributionfailures. As an example, if at least a certain number (e.g., a minimumof 3 or 4) of intelligent luminaire managers 112 or RF devices within apredetermined distance (e.g., 400-500 ft radius) or other geographiclocation all have communication problems with an overlapping period oftime (e.g., the same hour), then the network operation center 106 maydetermine that there is a system-level problem. In an example embodimentof the invention, the network operation center 106 may notify a utilitycompany, system owner/operators 108, maintenance personnel, and/oranother entity of the determined system-level problem.

In yet another example embodiment of the invention, an intelligentluminaire manager 112 or RF device may have a back-up power source suchas a battery. Accordingly, the intelligent luminaire manager 112 or RFdevice may still be operative for a limited time if the primary power(e.g., a line voltage) fails. In an example embodiment of the invention,if the intelligent luminaire manager 112 or RF device loses primarypower, then the intelligent luminaire manager 112 or RF device maytransmit a no-power alarm to the network operation center 106 via thenetwork 102. In an example embodiment of the invention, the networkoperation center 106 may receive a plurality of no-power alarms from arespective plurality of intelligent luminaire managers 112 or RFdevices. The network operation center 106 can then analyze the pluralityof no-power alarms according to geographical location and time offailure. As an example, if the network operation center 106 determinesthat a predetermined number of intelligent luminaire managers or RFdevices within a predetermined distance (e.g., 400-500 ft radius) orother geographic location all have non-power alarms with an overlappingperiod of time (e.g., the same hour), then the network operation center106 may determine a mass power outage or other system-level problem. Inan example embodiment of the invention, the network operation center 106may notify a utility company, system owner/operators 108, maintenancepersonnel, and/or another entity of the determined system-level problem.

In addition to the communications diagnostics described above, thenetwork operation center 106 may also be operative to performsystem-level diagnostics relating to power and distribution. Accordingto an example embodiment of the invention, the network operation center106 may be able to identify equipment or fixtures that operate on groupcontrol. With group control, a plurality of equipment or fixtures suchas luminaires may be similarly operated in a group using a singlephoto-control, timer, relay, or other control device. However, it maynot be desirable to use group control when a respective intelligentluminaire manager 112 or other RF device has been provided for or iscommunication with a respective equipment, fixture, or a luminaire.

In diagnosing a group control configuration, the network operationcenter 106 may compare the reports or messages received from theintelligent luminaire managers 112 or other RF device during a timeperiod (e.g., a day) against expected reports or messages. For example,if the network operation center 106 consistently (e.g., greater than 3days in a row or some other time period) receives reports or messages(e.g., hourly reports) from a first intelligent luminaire manager 112 orRF device during a first time period (e.g., each night), but none duringa second time period (e.g., during daylight)—that is, there is nocommunications during the second time period, then the network operationcenter 106 may determine that a first equipment, fixture, or luminaireassociated with the first intelligent luminaire manager or RF device ispotentially on a group control configuration. In addition, the networkoperation center 106 may also determine, based upon the received reportsfrom at least one second intelligent luminaire manager 112 or RF device,that at least one second equipment, fixture, or luminaire in theproximity of the first equipment, fixture, or luminaire is operating ina similar pattern or schedule (e.g., communications during night, butnone during the day) as the first equipment, fixture, or luminaire. Inthis situation, the network operation center may determine that thefirst equipment, fixture, or luminaire and the at least one secondequipment, fixture, or luminaire that are in proximity to each other arein a group control configuration. In an example embodiment of theinvention, the network operation center 106 may notify a systemowner/operator 108 or maintenance personnel of the group controlconfiguration, and a location of the equipment, fixtures, or luminairesassociated therewith.

According to an example embodiment of the invention, the networkoperation center 106 may also be operative to diagnose a powerdistribution quality problem. The network operation center 106 mayreceive periodic reports or messages (e.g., 30-minute reports, hourlyreports, etc.) from an intelligent luminaire manager 112 or other RFdevice. The periodic reports or messages may include voltageinformation, including a line voltage detected by a voltage sensor ofthe intelligent luminaire manager 112 or other RF device. The networkoperation center 106 may then record the received voltage information(e.g., line voltage) in association with a time (e.g., approximate timethe voltage information was measured or received). Based upon thereceived voltage information, the network operation center 106 maydetermine if the received voltage (e.g., line voltage) is too high(e.g., exceeds a first threshold) or too low (e.g., is below a secondthreshold). The thresholds for determining a high or low voltagecondition may be set by an entity such as the owner/operator 108 orotherwise determined based upon the activation information, as describedherein. A high voltage condition or a low voltage condition may berecorded by the network operation center 106.

In addition, since the network operation center 106 records the voltageinformation received from the intelligent luminaire manager 112 during aplurality of time periods, the network operation center 106 can alsodetermine whether the change in voltage is acceptable. For example, thenetwork operation center 106 may calculate a change in line voltageV_(LINE) between the high and lowest line voltages for a one-hour periodor another period. If the change in line voltage V_(LINE) exceeds amaximum acceptable amount or threshold, then the network operationcenter may determine a power quality problem. In an example embodimentof the invention, the network operation center 106 may notify a systemowner/operator 108 or maintenance personnel of the power quality problemand/or detected high voltages or low voltages.

In addition, the network operation center 106 may also leveragesystem-level knowledge of power quality problems associated with aplurality of intelligent luminaire managers 112 or RF devices, orfixtures or equipment in communications with the luminaire mangers 112or RF devices. In particular, if the power quality problems arise in aconfined geographical area or are other provided in a particulargroupings or configuration (or within a predetermined distance) within asubstantially same or overlapping time period, then the networkoperation center may be able to diagnose or detect a power distributionquality problem on a particular branch circuit or confined geographicalarea.

It will be appreciated that the aforementioned diagnostics and yet otherdiagnostics may be performed by the network operation center 106. Inaddition, while the example diagnostics may have been discussed in thecontext of an intelligent luminaire manager 112 monitoring a luminaire,the example diagnostics are applicable generally to many RF devices incommunications with equipment. The RF devices may utilize a networksimilar to the network (e.g., mesh network, etc.) formed by thenetworked intelligent luminaire managers described herein.Alternatively, the RF devices may join the network of networkedintelligent luminaire managers, as described herein. Example equipmentin communication with or otherwise monitored by the RF device mayinclude utility equipment such as gas, electric, water meters, parkingmaters, or yet other meters. Other example equipment is availablewithout departing from example embodiments of the invention.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. An intelligent luminaire manager, comprising: a voltage sensor formeasuring a voltage provided to a luminaire; a current sensor formeasuring a current provided to the luminaire; a controller configuredto receive voltage information corresponding to the voltage measured bythe voltage sensor and current information corresponding to the currentmeasured by the current sensor; a luminaire diagnostic program stored ina memory of the controller, wherein the luminaire diagnostic program isoperative to: compute a first average real power based upon the receivedvoltage information and the received current information for a firsttime period; compute a second average real power based upon the receivedvoltage information and the received current information for a secondtime period subsequent to the first time period; determine whether thesecond average real power has increased beyond the first average realpower by at least a preset amount; and generate a fixture statusindication associated with the luminaire based upon the determination.2. The intelligent luminaire manager of claim 1, wherein the presetamount is a percentage of the computed initial average real power. 3.The intelligent luminaire manager of claim 1, wherein the second averagereal power is determined to not have increased beyond the initialaverage real power by the preset amount, and wherein the luminairediagnostic program is further configured to: determine that the secondaverage real power does not exceed a threshold value, wherein thefixture status indication is set to indicate a bad fixture.
 4. Theintelligent luminaire manager of claim 1, wherein the second averagereal power is determined to not have increased beyond the initialaverage real power by the preset amount, and wherein the luminairediagnostic program is further configured to: determine that the secondaverage real power exceeds a threshold value, wherein the fixture statusindication is set to indicate an installation of a non-HID(high-intensity discharge) lamp.
 5. The intelligent luminaire manager ofclaim 1, wherein the first time period begins after a predetermineddelay period following a directive from the controller to turn on theluminaire.
 6. The intelligent luminaire manager of claim 1, wherein thegenerated fixture status is wirelessly transmitted to a network servervia a network of networked intelligent luminaire managers.
 7. Theintelligent luminaire manager of claim 1, wherein the initial averagereal power or the second average real power value is computed based atleast in part upon by averaging a plurality of instantaneous real powervalues, wherein each instantaneous real power value is determined from aproduct of a voltage value and a current value, wherein the voltagevalue is included in the received voltage information and the currentvalue is included in the received current information.
 8. Theintelligent luminaire manager of claim 1, wherein the determination ofwhether the second average real power has increased beyond the firstaverage real power value by at least the preset amount comprises:calculating a magnitude of a difference between the second average realpower and the first average real power; and comparing the calculatedmagnitude to the preset amount.
 9. An intelligent luminaire manager,comprising: a voltage sensor for measuring a voltage provided to aluminaire; a current sensor for measuring a current provided to theluminaire; a controller configured to receive voltage informationcorresponding to the voltage measured by the voltage sensor and currentinformation corresponding to the current measured by the current sensor;a luminaire diagnostic program stored in a memory of the controller,wherein the luminaire diagnostic program is operative to: update areference power value based upon an average real power computed usingthe received voltage information and the received current information;compute a current real power based upon the received voltage informationand the received current information; and increment a cycling counterbased upon determining, while the luminaire is associated with an ONstate, that the current real power is less than a first thresholdassociated with the reference power value; and identify a cycling faultbased upon the cycling counter exceeding a second threshold.
 10. Theintelligent luminaire manager of claim 9, wherein the first threshold isa predetermined percentage or fraction of the reference power value. 11.The intelligent luminaire manager of claim 9, wherein the average realpower is computed within a predetermined time period range from thecomputation of the current real power.
 12. The intelligent luminairemanager of claim 11, wherein the luminaire diagnostic program isoperative to: update the reference power value when the computed averagereal power exceeds an existing value of the reference power value. 13.The intelligent luminaire manager of claim 11, wherein an indication ofthe cycling fault is wirelessly transmitted to a network server via anetwork of networked intelligent luminaire managers. 14-20. (canceled)